Version Management > Version Management Overview > Version Manager > Version Management Files > Rsq File (.rsq)

Rsq File (.rsq)

An .rsq file is a site-specific .rsp file. The .rsq file contains entries that are unique to an installation, such as COM objects, CygNet ActiveX controls, third-party ActiveX controls, .NET Framework assemblies, or DDS editors. The .rsq file must have the same name as the .rsp file. The relationship is implicit. If the file exists, it will be checked during version management.

An .rsp file may be replaced with a new one during an upgrade. Since .rsq files are site specific, they are not replaced.

Be aware that the timestamp is also the trigger to check a .rsq file, so it would require an update when the file contents change.

Custom .rsq Entry Examples

You can modify the .rsq file for any CygNet client or utility to include other files or assemblies so they will be checked during version management. The following sections describe some of the different file types you can include.

See Version Manager Installation Parameters for more information about the operation parameters included in these examples.

COM Objects

You can include COM objects (.dll or .ocx files) in an .rsq, which will get registered into the registry using the <REGISTER> keyword. Say, you have built a CygNet Studio screen that uses the CxVhs.dll control. The .dll will need to be included in version management so it is distributed to users. To accomplish this, you would edit the CStudio.rsq and list the CxVhs.dll file. An example of the .rsq entry is shown below.

# Installation specific version management file for CygNet Studio

# Add any custom entries to this file to ensure changes are not lost in the next update process.

 

[SUPPORT]..\SUPPORT\CxVhs.dll <REGISTER>

.NET Assemblies

It is also possible to version manage .NET Framework assemblies. These .dlls can live in the same directory as the application, or are put into the Windows Global Assembly Cache (GAC) using the <GACINSTALL> keyword. Edit an .rsq file to include the desired .NET .dll, as shown in the following example:

# CygNet internal shared UI files

[SUPPORT]..\SUPPORT\CygNet.UI.dll <GACINSTALL> <DOT_NET_REQ=4.0>

.NET Assemblies that are COM Visible

These .dll files are basically a single assembly that merges the above two functions. They can be placed in the GAC for use in .NET Framework code using the <GACINSTALL> keyword, or they can be registered using the <REGASM> keyword for use outside of .NET in the same manner as a COM object. Or both. Edit an .rsq file to include the desired CygNet.API assemblies or .dll file, as shown in the following example:

# CygNet API and .Net COM files

[API]..\Bin\CygNet.Core.dll <GACINSTALL> <DOT_NET_REQ=4.0>

[API]..\Bin\CygNet.Data.Core.dll <GACINSTALL> <REGASM> <DOT_NET_REQ=4.0> <ARCHITECTURE_TYPE=x86>

[API]..\Bin\CygNet.API.Core.dll <GACINSTALL> <DOT_NET_REQ=4.0>

[API]..\Bin\CygNet.API.Core32.dll <GACINSTALL> <DOT_NET_REQ=4.0>

[API]..\Bin\CygNet.Data.ServiceManager.dll <GACINSTALL> <REGASM> <DOT_NET_REQ=4.0> <ARCHITECTURE_TYPE=x86>

[API]..\Bin\CygNet.API.ServiceManager.dll <GACINSTALL> <REGASM> <DOT_NET_REQ=4.0> <ARCHITECTURE_TYPE=x86>

[API]..\Bin\CygNet.API.ServiceManager32.dll <GACINSTALL> <DOT_NET_REQ=4.0>

 

# CygNet Redundancy Editors files

[SUPPORT]..\SUPPORT\CygNetRedundancyEditors.dll <GACINSTALL> <REGASM> <DOT_NET_REQ=4.0> <ARCHITECTURE_TYPE=x86>

See Operation Parameters for more information about the parameters shown about.

CxDdsEditors.rsq

Another commonly used .rsq file is CxDdsEditors.rsq. Edit the .rsq file to lists the EIE editors specific to a host, as shown in the following example:

#Site-specific CxDdsEditors.rsq file

##################################################################################

# NOTE: For the EIE editors below that are commented out, you should un-comment

# only those entries which are relevant to your installation. These entries

# exist in this file instead of the RSP file since RSP file changes would most

# likely be lost when applying future updates. This is because RSP files are

# over-written in the update process but RSQ files are not.

##################################################################################

[SUPPORT]..\SUPPORT\CxDdsAllenBradleyCIPEditors.rsp

[SUPPORT]..\SUPPORT\CxDdsAllenBradleyEditors.rsp

[SUPPORT]..\SUPPORT\CxDdsAm1000Editors.rsp

[SUPPORT]..\SUPPORT\CxDdsAm300Editors.rsp

[SUPPORT]..\SUPPORT\CxDdsAm700Editors.rsp

[SUPPORT]..\SUPPORT\CxDdsBenchmarkEditors.rsp

[SUPPORT]..\SUPPORT\CxDdsBsapEditors.rsp

[SUPPORT]..\SUPPORT\CxDdsEFM3000Editors.rsp

[SUPPORT]..\SUPPORT\CxDdsElfEditors.rsp

[SUPPORT]..\SUPPORT\CxDdsEmersonRocEditors.rsp

[SUPPORT]..\SUPPORT\CxDdsEmersonRocPlusEditors.rsp

.

.

.

Back to top

Let us know how we can improve this topic.

CygNet at weatherford.com

© 2020 Weatherford. All rights reserved.